13.2.2 Stage 2 Ordering

In this phase, the endorsed transactions in stage – I are sent to the

orderer(s) from many different applications running concurrently. The

orderer collects all the endorsed transactions, orders them

ascendingly, and packages them into blocks, where the maximum

transactions per block can be adjusted through configuration. These

blocks can be saved to the orderer’s ledger, and later, can be

distributed to all the peers associated to the channel.

13.2.3 Stage 3 Validation & Commit

In this phase, the blocks are actually relayed to all the associated

peers. The peers then can validate these transactions themselves

and commit these transactions to their respective ledger, and finally,

they can reach a common consensus.

Ideally, an application connects to one or more endorsing peers

within a channel with a transaction. The peers invoke a smart

contract associated with that peer, get the related ledger updated,

and send a response back to the application.

Please note that this consensus part is very important for the

developers, especially to understand how to club every piece

together for integration. Figure 13.4 represents the entire end-to-end

ecosystem of Hyperledger Fabric along with the other layers that

invoke it, as shown as follows:

Figure 13.4: Hyperledger Fabric in integration with other layers

13.3 Private Data